Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f2724a1647b4edd10b26ca42b9c1dd811d2aa31b0037aa28492df5c871c8e2

Tx prefix hash: 021f4ef93e38e85465616cc263387ee9f3c3bb431ea1f4b4132a0343588a7ddc
Tx public key: 18a09ec03831a62351b9eeb23b3cfa8680a4fa819ed0dda24091aa69382beae5
Timestamp: 1722462050 Timestamp [UCT]: 2024-07-31 21:40:50 Age [y:d:h:m:s]: 00:176:03:45:33
Block: 1077962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125993 RingCT/type: yes/0
Extra: 0118a09ec03831a62351b9eeb23b3cfa8680a4fa819ed0dda24091aa69382beae5021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be9f1b5b46693f278f1d750947c720b7d5e6856f3ada5cb24c02be2bac586c46 0.600000000000 1550517 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": 1077972, "vin": [ { "gen": { "height": 1077962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be9f1b5b46693f278f1d750947c720b7d5e6856f3ada5cb24c02be2bac586c46" } } ], "extra": [ 1, 24, 160, 158, 192, 56, 49, 166, 35, 81, 185, 238, 178, 59, 60, 250, 134, 128, 164, 250, 129, 158, 208, 221, 162, 64, 145, 170, 105, 56, 43, 234, 229, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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