Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b04e67a9bc2a9150bec77ec755c6d1674738de17577211c21fee49705aac8f51

Tx prefix hash: 1647b3f649b7540da81312b07bb730192b8409918b303fc73419ad6aa4f859ed
Tx public key: 33531b01d04b5bf1e7bb838c686067c9d4e5d55db5a5d169fdcbb1d2b50b77ca
Timestamp: 1732194656 Timestamp [UCT]: 2024-11-21 13:10:56 Age [y:d:h:m:s]: 00:002:17:25:42
Block: 1158554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1952 RingCT/type: yes/0
Extra: 0133531b01d04b5bf1e7bb838c686067c9d4e5d55db5a5d169fdcbb1d2b50b77ca0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6ba552d11e5fa94d9e0f60351f060cec5dce34e61ec81470507ae1ac41620d9 0.600000000000 1644183 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": 1158564, "vin": [ { "gen": { "height": 1158554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ba552d11e5fa94d9e0f60351f060cec5dce34e61ec81470507ae1ac41620d9" } } ], "extra": [ 1, 51, 83, 27, 1, 208, 75, 91, 241, 231, 187, 131, 140, 104, 96, 103, 201, 212, 229, 213, 93, 181, 165, 209, 105, 253, 203, 177, 210, 181, 11, 119, 202, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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