Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0f6434d64b8f555900b76f74451ab59b3f0fcfbc30f1bdaa8ba70192cffcde

Tx prefix hash: 4592bd6b6dec42a12031ea8fa1cd801bce34dc739a1f40b1fda4749d6b7b184d
Tx public key: d554329d6f341402c753d4186f1cd478dbe4e6d4ce82c73edaac6dbb6d38f962
Timestamp: 1745959481 Timestamp [UCT]: 2025-04-29 20:44:41 Age [y:d:h:m:s]: 00:247:03:54:55
Block: 1272262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174417 RingCT/type: yes/0
Extra: 01d554329d6f341402c753d4186f1cd478dbe4e6d4ce82c73edaac6dbb6d38f96202110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d642fea469782dc172b713a4779942d109ef1593d92be435bab9b477a10f9aa 0.600000000000 1759535 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": 1272272, "vin": [ { "gen": { "height": 1272262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d642fea469782dc172b713a4779942d109ef1593d92be435bab9b477a10f9aa" } } ], "extra": [ 1, 213, 84, 50, 157, 111, 52, 20, 2, 199, 83, 212, 24, 111, 28, 212, 120, 219, 228, 230, 212, 206, 130, 199, 62, 218, 172, 109, 187, 109, 56, 249, 98, 2, 17, 0, 0, 0, 5, 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