Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ac9a0b779ac9eaea6615a309438d22562667a7eb0047692a9e8ddc44b0f178

Tx prefix hash: 96e8651fc8fcded6785d2266372844b5eb4ea6894e2310f8ce00b71ce70e043e
Tx public key: 998c3ce4a9a3c796534acaadbaaca39a8e088e715c2c94dbdcad9a2a1019e3ac
Timestamp: 1736135854 Timestamp [UCT]: 2025-01-06 03:57:34 Age [y:d:h:m:s]: 00:301:17:27:41
Block: 1191201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213129 RingCT/type: yes/0
Extra: 01998c3ce4a9a3c796534acaadbaaca39a8e088e715c2c94dbdcad9a2a1019e3ac02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19d927bd4683d48409f3827b5f985435106624743a1b44cad9d81ae01f0e3e2b 0.600000000000 1677724 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": 1191211, "vin": [ { "gen": { "height": 1191201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19d927bd4683d48409f3827b5f985435106624743a1b44cad9d81ae01f0e3e2b" } } ], "extra": [ 1, 153, 140, 60, 228, 169, 163, 199, 150, 83, 74, 202, 173, 186, 172, 163, 154, 142, 8, 142, 113, 92, 44, 148, 219, 220, 173, 154, 42, 16, 25, 227, 172, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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