Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d570a0b5e5ac51a5fd6cdad95d8e213f7697433c69afd57e27f05300fd6786

Tx prefix hash: 869fb1597b376b814b8800a58469dda57ae6c15516d82eda5d227ca51e0b4031
Tx public key: 05a4f8804374f37ad1d370cb1ba4031e71bdaaf1bdfbe39b739cf40da1f8dcf5
Timestamp: 1745403363 Timestamp [UCT]: 2025-04-23 10:16:03 Age [y:d:h:m:s]: 00:016:18:56:22
Block: 1267645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12012 RingCT/type: yes/0
Extra: 0105a4f8804374f37ad1d370cb1ba4031e71bdaaf1bdfbe39b739cf40da1f8dcf502110000000a6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2729f2fd8ac3b20af8277e3bde8fac1199d0d674619fa2caf0396e2c6b1ca4a7 0.600000000000 1754874 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": 1267655, "vin": [ { "gen": { "height": 1267645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2729f2fd8ac3b20af8277e3bde8fac1199d0d674619fa2caf0396e2c6b1ca4a7" } } ], "extra": [ 1, 5, 164, 248, 128, 67, 116, 243, 122, 209, 211, 112, 203, 27, 164, 3, 30, 113, 189, 170, 241, 189, 251, 227, 155, 115, 156, 244, 13, 161, 248, 220, 245, 2, 17, 0, 0, 0, 10, 108, 152, 170, 61, 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