Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6530e06474729d53f9362f4cb6d111aa7f20270546db4d26c010999b5bee074c

Tx prefix hash: 951b4e21cea11566a825850b24d148589d15582c354d9a5f265909db7582354d
Tx public key: dabb3e7aa9510744daa7fb20111d2416d35805aea0c55ba0558cb7462df0fa55
Timestamp: 1755669170 Timestamp [UCT]: 2025-08-20 05:52:50 Age [y:d:h:m:s]: 00:084:15:12:23
Block: 1350380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60384 RingCT/type: yes/0
Extra: 01dabb3e7aa9510744daa7fb20111d2416d35805aea0c55ba0558cb7462df0fa550211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d8125b0d271cd0b4e242c5b8053fe5d2aa26d68a676ef7808bcc9b4befc14e5 0.600000000000 1838325 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": 1350390, "vin": [ { "gen": { "height": 1350380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d8125b0d271cd0b4e242c5b8053fe5d2aa26d68a676ef7808bcc9b4befc14e5" } } ], "extra": [ 1, 218, 187, 62, 122, 169, 81, 7, 68, 218, 167, 251, 32, 17, 29, 36, 22, 211, 88, 5, 174, 160, 197, 91, 160, 85, 140, 183, 70, 45, 240, 250, 85, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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