Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f07e500213b4774aeb3a20ac703832a174ffe8e86d7b64bebd67c6330dc5fae

Tx prefix hash: 937e5d0161c01c18a9f229d44765efcb91364d1874a4d250ef8fef4d24699849
Tx public key: 9e32a818cd9372a8e3c172e94f80ca2243a7547a7ff48e4101c2d0a1fa247ad3
Timestamp: 1745087009 Timestamp [UCT]: 2025-04-19 18:23:29 Age [y:d:h:m:s]: 00:208:14:28:57
Block: 1265053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146787 RingCT/type: yes/0
Extra: 019e32a818cd9372a8e3c172e94f80ca2243a7547a7ff48e4101c2d0a1fa247ad3021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d1b0c680130803aebc47572aa0e1d7c05e94229ad3b0480d919605a26a25fcc 0.600000000000 1752256 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": 1265063, "vin": [ { "gen": { "height": 1265053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d1b0c680130803aebc47572aa0e1d7c05e94229ad3b0480d919605a26a25fcc" } } ], "extra": [ 1, 158, 50, 168, 24, 205, 147, 114, 168, 227, 193, 114, 233, 79, 128, 202, 34, 67, 167, 84, 122, 127, 244, 142, 65, 1, 194, 208, 161, 250, 36, 122, 211, 2, 17, 0, 0, 0, 4, 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