Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee61e0005b9d55f172f0582cb1c3449192c8ca08634277b529598df3ffb3cfcd

Tx prefix hash: 430763e9722b002b4c3b9c7e4bdb8b1f71b19716a6fe322eb411bc5340a68c95
Tx public key: 7aa600f77c47fd31c4f4b92d321892d50cb0a7afd5656ad80c43d0edff989cd4
Timestamp: 1636962201 Timestamp [UCT]: 2021-11-15 07:43:21 Age [y:d:h:m:s]: 03:012:14:56:31
Block: 374678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 787743 RingCT/type: yes/0
Extra: 017aa600f77c47fd31c4f4b92d321892d50cb0a7afd5656ad80c43d0edff989cd402110000001ae9564d6f000000000000000000

1 output(s) for total of 35.199511567000 dcy

stealth address amount amount idx
00: 0f4d67613a5d620976cc4b99d28254d871787c3ead43967bb244ad1db4c45bd0 35.199511567000 758318 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": 374688, "vin": [ { "gen": { "height": 374678 } } ], "vout": [ { "amount": 35199511567, "target": { "key": "0f4d67613a5d620976cc4b99d28254d871787c3ead43967bb244ad1db4c45bd0" } } ], "extra": [ 1, 122, 166, 0, 247, 124, 71, 253, 49, 196, 244, 185, 45, 50, 24, 146, 213, 12, 176, 167, 175, 213, 101, 106, 216, 12, 67, 208, 237, 255, 152, 156, 212, 2, 17, 0, 0, 0, 26, 233, 86, 77, 111, 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