Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 613da28d84f20c49c77b8dfdad977ed6dfd687f09582ff625f21bbd7b7c317ca

Tx prefix hash: 871c8a11353338281733087a6a164172747b9dcbbf2f2f4b8ce0bf33ed2f754e
Tx public key: 854e67ef23f10bb8ccc3dc23bb4f3117cd67d9dc02585967a6c0ef583c1c019c
Timestamp: 1602481093 Timestamp [UCT]: 2020-10-12 05:38:13 Age [y:d:h:m:s]: 04:046:14:32:01
Block: 140707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1021644 RingCT/type: yes/0
Extra: 01854e67ef23f10bb8ccc3dc23bb4f3117cd67d9dc02585967a6c0ef583c1c019c02110000014af8cbd8e0000000000000000000

1 output(s) for total of 209.787691043000 dcy

stealth address amount amount idx
00: c51df2022f871eed5b796c57f103ca1cbea4eeff44cfbf6ca8d9894d03cf2b7e 209.787691043000 233708 of 0

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": 140717, "vin": [ { "gen": { "height": 140707 } } ], "vout": [ { "amount": 209787691043, "target": { "key": "c51df2022f871eed5b796c57f103ca1cbea4eeff44cfbf6ca8d9894d03cf2b7e" } } ], "extra": [ 1, 133, 78, 103, 239, 35, 241, 11, 184, 204, 195, 220, 35, 187, 79, 49, 23, 205, 103, 217, 220, 2, 88, 89, 103, 166, 192, 239, 88, 60, 28, 1, 156, 2, 17, 0, 0, 1, 74, 248, 203, 216, 224, 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