Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bc29b654d6bef102b1b2112cbd53ba7730c4c7c8d1910e9aef493f446b41dab

Tx prefix hash: bc289a0c30fa32a63a7b2776ff9969af90411c4eb4985d871d73589e969f664f
Tx public key: 35041d80e9224a897879816e7318832f90e80b9341aa4c295d5fb3a6e18d7be5
Timestamp: 1732029458 Timestamp [UCT]: 2024-11-19 15:17:38 Age [y:d:h:m:s]: 00:135:20:46:26
Block: 1157193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96919 RingCT/type: yes/0
Extra: 0135041d80e9224a897879816e7318832f90e80b9341aa4c295d5fb3a6e18d7be5021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4382bf12f6d29f4730f873ffaf33bc77232ef7d724da5b5d4ac011e12b464fa6 0.600000000000 1642816 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": 1157203, "vin": [ { "gen": { "height": 1157193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4382bf12f6d29f4730f873ffaf33bc77232ef7d724da5b5d4ac011e12b464fa6" } } ], "extra": [ 1, 53, 4, 29, 128, 233, 34, 74, 137, 120, 121, 129, 110, 115, 24, 131, 47, 144, 232, 11, 147, 65, 170, 76, 41, 93, 95, 179, 166, 225, 141, 123, 229, 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