Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11d0f6130bcd684d6b43ff351ae97efddc2ede45bb47159cc3ea69990b619cfd

Tx prefix hash: c610f45184e8fd4c3d92b6b950c4c64c6645a7e681bc152288e65292a62de2bc
Tx public key: cd3a05e2d3ded5d21f2a4de0b7aa3ae945b3ecba58823560fcef00ad64781c6f
Timestamp: 1745266069 Timestamp [UCT]: 2025-04-21 20:07:49 Age [y:d:h:m:s]: 00:280:19:58:29
Block: 1266512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198351 RingCT/type: yes/0
Extra: 01cd3a05e2d3ded5d21f2a4de0b7aa3ae945b3ecba58823560fcef00ad64781c6f021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d871d4870d11243b4af32599b59a261558526fe8b1abadd06a86815f07237ff3 0.600000000000 1753733 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": 1266522, "vin": [ { "gen": { "height": 1266512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d871d4870d11243b4af32599b59a261558526fe8b1abadd06a86815f07237ff3" } } ], "extra": [ 1, 205, 58, 5, 226, 211, 222, 213, 210, 31, 42, 77, 224, 183, 170, 58, 233, 69, 179, 236, 186, 88, 130, 53, 96, 252, 239, 0, 173, 100, 120, 28, 111, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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