Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26ed05201a4d3ca7cb46d8d7ca5957c8325d7f5bfb27a4fb5f88a876f7d34436

Tx prefix hash: bbfac201be878d8e34c56d95ba5aa926f61318fd17484ee24ce84753cc4214f5
Tx public key: 49b98c091221c68c0d47dcb3d00f8dc7f64db7b926e9043701cb661fc8adc5c8
Timestamp: 1732939672 Timestamp [UCT]: 2024-11-30 04:07:52 Age [y:d:h:m:s]: 00:029:13:48:28
Block: 1164739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21142 RingCT/type: yes/0
Extra: 0149b98c091221c68c0d47dcb3d00f8dc7f64db7b926e9043701cb661fc8adc5c8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d73e8c19d1a143fcaaf9e9b784eee0b675ed8b9a518c7a90e65aa61ca08eb8bd 0.600000000000 1650414 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": 1164749, "vin": [ { "gen": { "height": 1164739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73e8c19d1a143fcaaf9e9b784eee0b675ed8b9a518c7a90e65aa61ca08eb8bd" } } ], "extra": [ 1, 73, 185, 140, 9, 18, 33, 198, 140, 13, 71, 220, 179, 208, 15, 141, 199, 246, 77, 183, 185, 38, 233, 4, 55, 1, 203, 102, 31, 200, 173, 197, 200, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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