Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de720fe4e92b8add2cf7334eb1d05dfbf513bf3937d97d19588cddc004f31512

Tx prefix hash: 774f65e895b7a0b705ac1a7759187ceeb4b0a28ca5f684990ace2af56e828dea
Tx public key: 281e0ecb81e34d9c2d1354307ddcb4d4964f0b1113a1af1a2a06fdba894b7495
Timestamp: 1738131004 Timestamp [UCT]: 2025-01-29 06:10:04 Age [y:d:h:m:s]: 00:326:05:51:58
Block: 1207457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230963 RingCT/type: yes/0
Extra: 01281e0ecb81e34d9c2d1354307ddcb4d4964f0b1113a1af1a2a06fdba894b74950211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed634263dccdb20c847100e002ea9f5124bfdc553d847f5b08ee13f4e11ade5 0.600000000000 1694180 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": 1207467, "vin": [ { "gen": { "height": 1207457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed634263dccdb20c847100e002ea9f5124bfdc553d847f5b08ee13f4e11ade5" } } ], "extra": [ 1, 40, 30, 14, 203, 129, 227, 77, 156, 45, 19, 84, 48, 125, 220, 180, 212, 150, 79, 11, 17, 19, 161, 175, 26, 42, 6, 253, 186, 137, 75, 116, 149, 2, 17, 0, 0, 0, 8, 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