Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ddc978767ecdf82205ac6587e7a300dd2c754d936626e99c199b06bab72bc2

Tx prefix hash: 682c9edcdc7e9a16b81cb43f8cc628b327f5c9465d3256dd9c5788e777718177
Tx public key: bbd29ec52b11c5e94299bf50ae9fcf156d1e87d5dfc6d428c6b2a9ba2935cc99
Timestamp: 1733579573 Timestamp [UCT]: 2024-12-07 13:52:53 Age [y:d:h:m:s]: 00:142:18:56:29
Block: 1170033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101878 RingCT/type: yes/0
Extra: 01bbd29ec52b11c5e94299bf50ae9fcf156d1e87d5dfc6d428c6b2a9ba2935cc99021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b02e4a4dffc486ffce0c557a147f51057a03dc84ca050f7842edd918ab178b5 0.600000000000 1655760 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": 1170043, "vin": [ { "gen": { "height": 1170033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b02e4a4dffc486ffce0c557a147f51057a03dc84ca050f7842edd918ab178b5" } } ], "extra": [ 1, 187, 210, 158, 197, 43, 17, 197, 233, 66, 153, 191, 80, 174, 159, 207, 21, 109, 30, 135, 213, 223, 198, 212, 40, 198, 178, 169, 186, 41, 53, 204, 153, 2, 17, 0, 0, 0, 1, 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