Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d6b04bf4843b38d697cd83b6fdb7cc3ca26ac2ce7c08b85a36e627aeeccbd4

Tx prefix hash: 4caedd7180172db4c372c48af8ae55e72fda9f004705e9cdde402743257b8521
Tx public key: 13e16f5cf6d9be1361885a8c136e9c05b63e0544e872b74f617e379c984b366e
Timestamp: 1735504940 Timestamp [UCT]: 2024-12-29 20:42:20 Age [y:d:h:m:s]: 00:099:00:20:02
Block: 1185962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70546 RingCT/type: yes/0
Extra: 0113e16f5cf6d9be1361885a8c136e9c05b63e0544e872b74f617e379c984b366e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 685ec631b3bccfde0edb2a48192e39e32fd39bf4e47b54015f6c72a907a70416 0.600000000000 1672437 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": 1185972, "vin": [ { "gen": { "height": 1185962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "685ec631b3bccfde0edb2a48192e39e32fd39bf4e47b54015f6c72a907a70416" } } ], "extra": [ 1, 19, 225, 111, 92, 246, 217, 190, 19, 97, 136, 90, 140, 19, 110, 156, 5, 182, 62, 5, 68, 232, 114, 183, 79, 97, 126, 55, 156, 152, 75, 54, 110, 2, 17, 0, 0, 0, 2, 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