Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5ac6984e13c88fa0cf95fcebe1fd7ce02aad67d9d57dd468c3b208eddf3a090

Tx prefix hash: 93c63d6be3140debcb33f3cf7330bf53c89a62214b4e5bc6c63e5471b83b8679
Tx public key: 3d21c4c70bdef346f1b3dbe5e6d786c6316bad8fa4e99cf49941d32f2fbaeddc
Timestamp: 1582518957 Timestamp [UCT]: 2020-02-24 04:35:57 Age [y:d:h:m:s]: 05:251:11:13:44
Block: 71480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1330540 RingCT/type: yes/0
Extra: 013d21c4c70bdef346f1b3dbe5e6d786c6316bad8fa4e99cf49941d32f2fbaeddc02110000000156c366d3000000000000000000

1 output(s) for total of 355.760632653000 dcy

stealth address amount amount idx
00: c44a9bc21ce47d4eaab4a39e10745553cc51bdbdd57b4318244779a0bde947dd 355.760632653000 132003 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": 71490, "vin": [ { "gen": { "height": 71480 } } ], "vout": [ { "amount": 355760632653, "target": { "key": "c44a9bc21ce47d4eaab4a39e10745553cc51bdbdd57b4318244779a0bde947dd" } } ], "extra": [ 1, 61, 33, 196, 199, 11, 222, 243, 70, 241, 179, 219, 229, 230, 215, 134, 198, 49, 107, 173, 143, 164, 233, 156, 244, 153, 65, 211, 47, 47, 186, 237, 220, 2, 17, 0, 0, 0, 1, 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