Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de7d5fc8951dad155737b9a0c933a920bef985d280b5fa037f6c9f7f0c6abba

Tx prefix hash: 305ba408f967e4491dd051636d666b7153e43d38a3ad7ac0d005ffb801c787d2
Tx public key: e1d265904c02a663b02705c2e94964d17a14d527aadae09983cdae5fc94221e2
Timestamp: 1719856713 Timestamp [UCT]: 2024-07-01 17:58:33 Age [y:d:h:m:s]: 01:168:14:50:33
Block: 1056361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379093 RingCT/type: yes/0
Extra: 01e1d265904c02a663b02705c2e94964d17a14d527aadae09983cdae5fc94221e20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aafe2053101e7548132c43ab2b47aba4ecdd088fb04792444324918bd2ea1b1 0.600000000000 1526774 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": 1056371, "vin": [ { "gen": { "height": 1056361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aafe2053101e7548132c43ab2b47aba4ecdd088fb04792444324918bd2ea1b1" } } ], "extra": [ 1, 225, 210, 101, 144, 76, 2, 166, 99, 176, 39, 5, 194, 233, 73, 100, 209, 122, 20, 213, 39, 170, 218, 224, 153, 131, 205, 174, 95, 201, 66, 33, 226, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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