Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0b61b3feedba965dcae26ebe383dc79799386296086765bc760a54f4d72baa

Tx prefix hash: cc902ed8834ec55e91bd6d53f4ed6bb30b7b7a2a99e9db6db6a053d5a3afb2bd
Tx public key: 618fc578a81decb3721c23c12da5168ba82b9c89c9d357c0a8dd1180b02a3b25
Timestamp: 1746607342 Timestamp [UCT]: 2025-05-07 08:42:22 Age [y:d:h:m:s]: 00:197:10:15:18
Block: 1277617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138813 RingCT/type: yes/0
Extra: 01618fc578a81decb3721c23c12da5168ba82b9c89c9d357c0a8dd1180b02a3b2502110000000b1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2de1b3fa14d25ac63efbb1bc7c4914eeeaa3ba184395e50dcbeb43c8b7aba313 0.600000000000 1764974 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": 1277627, "vin": [ { "gen": { "height": 1277617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2de1b3fa14d25ac63efbb1bc7c4914eeeaa3ba184395e50dcbeb43c8b7aba313" } } ], "extra": [ 1, 97, 143, 197, 120, 168, 29, 236, 179, 114, 28, 35, 193, 45, 165, 22, 139, 168, 43, 156, 137, 201, 211, 87, 192, 168, 221, 17, 128, 176, 42, 59, 37, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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