Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a715213c6d028fb0230dbd4b52814efdbf1d10486264d6eda525b64f5149090

Tx prefix hash: c54734b4383b67c4841d6baf2b184ddeb8b4a32428e0fb623e97e33913dc7690
Tx public key: bf8e40914b7686ebf2dfb7f3d1d403cdb215888f071ceb2372c494cdd97d30f8
Timestamp: 1582249137 Timestamp [UCT]: 2020-02-21 01:38:57 Age [y:d:h:m:s]: 05:258:02:18:58
Block: 69094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1335438 RingCT/type: yes/0
Extra: 01bf8e40914b7686ebf2dfb7f3d1d403cdb215888f071ceb2372c494cdd97d30f802110000000356c366d3000000000000000000

1 output(s) for total of 362.296134789000 dcy

stealth address amount amount idx
00: a55f1906fe61af60103fd27f4e9a5a1b09b1a69dd0e12226cb277992faef06dc 362.296134789000 127434 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": 69104, "vin": [ { "gen": { "height": 69094 } } ], "vout": [ { "amount": 362296134789, "target": { "key": "a55f1906fe61af60103fd27f4e9a5a1b09b1a69dd0e12226cb277992faef06dc" } } ], "extra": [ 1, 191, 142, 64, 145, 75, 118, 134, 235, 242, 223, 183, 243, 209, 212, 3, 205, 178, 21, 136, 143, 7, 28, 235, 35, 114, 196, 148, 205, 217, 125, 48, 248, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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