Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7447fd299fd77f6abf4960ba37b37b31e226460705041fefcbdbb056a27753

Tx prefix hash: 67be6e0ca290bea9e5cd16b5264fb5ee407201c0f675dc15080993cfc1bdd0a7
Tx public key: e3b79278b7881ebe708adf4f04465b7963917b3c3daa5b5115e9cfc244a7c7ab
Timestamp: 1708252085 Timestamp [UCT]: 2024-02-18 10:28:05 Age [y:d:h:m:s]: 01:118:12:32:38
Block: 960160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345680 RingCT/type: yes/0
Extra: 01e3b79278b7881ebe708adf4f04465b7963917b3c3daa5b5115e9cfc244a7c7ab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 916df669f9bc5b6ff131c04708d551a285f53242f4e9ab6858dabe3f6ad80d38 0.600000000000 1419721 of 15

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": 960170, "vin": [ { "gen": { "height": 960160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "916df669f9bc5b6ff131c04708d551a285f53242f4e9ab6858dabe3f6ad80d38" } } ], "extra": [ 1, 227, 183, 146, 120, 183, 136, 30, 190, 112, 138, 223, 79, 4, 70, 91, 121, 99, 145, 123, 60, 61, 170, 91, 81, 21, 233, 207, 194, 68, 167, 199, 171, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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