Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4824334ad187b021bd3c1ecc2513f2f0cef1d699a531ab76cf305332272a5af1

Tx prefix hash: 450345a92715660cb3708aee7ba751315833f4344f650d8d633ec47523b73c21
Tx public key: 8f4136dd5805cb7cd7a24b4530d1b5e0f58fbba9dcb7ff2df142287c33ba6196
Timestamp: 1721093647 Timestamp [UCT]: 2024-07-16 01:34:07 Age [y:d:h:m:s]: 00:253:05:04:45
Block: 1066638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180863 RingCT/type: yes/0
Extra: 018f4136dd5805cb7cd7a24b4530d1b5e0f58fbba9dcb7ff2df142287c33ba619602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 994a2026e09758c7a41ff5eca9a42dcd67ed6131f11179b0ac3b109823e1b498 0.600000000000 1537305 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1066648, "vin": [ { "gen": { "height": 1066638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "994a2026e09758c7a41ff5eca9a42dcd67ed6131f11179b0ac3b109823e1b498" } } ], "extra": [ 1, 143, 65, 54, 221, 88, 5, 203, 124, 215, 162, 75, 69, 48, 209, 181, 224, 245, 143, 187, 169, 220, 183, 255, 45, 241, 66, 40, 124, 51, 186, 97, 150, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8