Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff5888747b8b0c677cb8d0f0eb3198cce365bcac680df40f769b794e7382a6b

Tx prefix hash: 8dcbd51de307707a2e3a191f043b0d759d5ad2c14cee642b0e17eff5733c9197
Tx public key: b1f060c07fc9cdcb1f09e59d161edbed42a24d7828817fd8a1e5f90449b04217
Timestamp: 1649401829 Timestamp [UCT]: 2022-04-08 07:10:29 Age [y:d:h:m:s]: 02:312:09:04:57
Block: 475673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742804 RingCT/type: yes/0
Extra: 01b1f060c07fc9cdcb1f09e59d161edbed42a24d7828817fd8a1e5f90449b04217021100000002a272b9cb000000000000000000

1 output(s) for total of 16.289139061000 dcy

stealth address amount amount idx
00: 798772da97eb6eef27a394a45649a30adfabc331dbdadb86144e976e01b07bc2 16.289139061000 895964 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": 475683, "vin": [ { "gen": { "height": 475673 } } ], "vout": [ { "amount": 16289139061, "target": { "key": "798772da97eb6eef27a394a45649a30adfabc331dbdadb86144e976e01b07bc2" } } ], "extra": [ 1, 177, 240, 96, 192, 127, 201, 205, 203, 31, 9, 229, 157, 22, 30, 219, 237, 66, 162, 77, 120, 40, 129, 127, 216, 161, 229, 249, 4, 73, 176, 66, 23, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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