Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a504fd39cc61179b00dcd10f480f2512f9104c646d3c889907c2d9276e608c8d

Tx prefix hash: 2fe6757166d0c35d2948d79ae3328cd02025025b6450d569f07b65885b2b849c
Tx public key: 858f43fd0acc2b0e763b426556c2ca56e2897b22c5379665e0a00a40705f0d4e
Timestamp: 1580977321 Timestamp [UCT]: 2020-02-06 08:22:01 Age [y:d:h:m:s]: 05:096:21:19:01
Block: 59715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221385 RingCT/type: yes/0
Extra: 01858f43fd0acc2b0e763b426556c2ca56e2897b22c5379665e0a00a40705f0d4e02110000000503d36d11000000000000000000

1 output(s) for total of 389.170789017000 dcy

stealth address amount amount idx
00: 8c921d3153647a0210ea6d374caccc93b9ce0755afa802726c0a4bd79ee27182 389.170789017000 110194 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": 59725, "vin": [ { "gen": { "height": 59715 } } ], "vout": [ { "amount": 389170789017, "target": { "key": "8c921d3153647a0210ea6d374caccc93b9ce0755afa802726c0a4bd79ee27182" } } ], "extra": [ 1, 133, 143, 67, 253, 10, 204, 43, 14, 118, 59, 66, 101, 86, 194, 202, 86, 226, 137, 123, 34, 197, 55, 150, 101, 224, 160, 10, 64, 112, 95, 13, 78, 2, 17, 0, 0, 0, 5, 3, 211, 109, 17, 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