Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b27d6507b189f7accefd3342d6826dfc15adf17d0696369416347bedecfe51

Tx prefix hash: be4d93d8a32bd64fb66e1c5b9af5e08a1010e97ff2fc4b8388944e11ac70b9ae
Tx public key: fc894e1ecca7653dcddf2e044bf6ebdf99cfafafddf2bdd9f7f28c70c16f326e
Timestamp: 1583810237 Timestamp [UCT]: 2020-03-10 03:17:17 Age [y:d:h:m:s]: 04:295:04:15:49
Block: 79577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105990 RingCT/type: yes/0
Extra: 01fc894e1ecca7653dcddf2e044bf6ebdf99cfafafddf2bdd9f7f28c70c16f326e02110000001d8a2ee0d9000000000000000000

1 output(s) for total of 334.463655376000 dcy

stealth address amount amount idx
00: 19b1cbd3cee2e9acf0e392fd4eb5bd911a45229e8bd6defaa0f63c3838f16f3e 334.463655376000 145613 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": 79587, "vin": [ { "gen": { "height": 79577 } } ], "vout": [ { "amount": 334463655376, "target": { "key": "19b1cbd3cee2e9acf0e392fd4eb5bd911a45229e8bd6defaa0f63c3838f16f3e" } } ], "extra": [ 1, 252, 137, 78, 30, 204, 167, 101, 61, 205, 223, 46, 4, 75, 246, 235, 223, 153, 207, 175, 175, 221, 242, 189, 217, 247, 242, 140, 112, 193, 111, 50, 110, 2, 17, 0, 0, 0, 29, 138, 46, 224, 217, 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