Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a60a45ceea454f776cc2d0cb51cf1e372345ec18cf4052e32e11aa4dc64973b

Tx prefix hash: 1c37b73b5e79f256f6c3137c0bad75a5a87742db89aaf267d0ae96adb36cb327
Tx public key: 0a22139d58c7c007b6807c4771546190ef3a32c4e4656993149d5c0d57e5bc47
Timestamp: 1737661888 Timestamp [UCT]: 2025-01-23 19:51:28 Age [y:d:h:m:s]: 00:350:14:52:03
Block: 1203783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248202 RingCT/type: yes/0
Extra: 010a22139d58c7c007b6807c4771546190ef3a32c4e4656993149d5c0d57e5bc4702110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 259aad1bd0403b92b18db1565e5d5b2eadb94f4dc1bc519200d14e009e904279 0.600000000000 1690462 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": 1203793, "vin": [ { "gen": { "height": 1203783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "259aad1bd0403b92b18db1565e5d5b2eadb94f4dc1bc519200d14e009e904279" } } ], "extra": [ 1, 10, 34, 19, 157, 88, 199, 192, 7, 182, 128, 124, 71, 113, 84, 97, 144, 239, 58, 50, 196, 228, 101, 105, 147, 20, 157, 92, 13, 87, 229, 188, 71, 2, 17, 0, 0, 0, 15, 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