Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53eb0880c0a7dba575f6bc248fd95763b4dd5c1802aeedc89175cdfd7e2704e6

Tx prefix hash: 10d0901e13697624cf6ea38ec63c906e059eee488a2530af33c974ecb07963f0
Tx public key: 764eba808407f8a70ebd82a67e71b3e874fc57fa2723e4dd3dc088d04bf97474
Timestamp: 1742306540 Timestamp [UCT]: 2025-03-18 14:02:20 Age [y:d:h:m:s]: 00:247:18:38:48
Block: 1242031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174793 RingCT/type: yes/0
Extra: 01764eba808407f8a70ebd82a67e71b3e874fc57fa2723e4dd3dc088d04bf974740211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcabdde081e5fa6a873bc145e52d075b8ef84899f4cebc01a16f0ba38e549a27 0.600000000000 1729004 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": 1242041, "vin": [ { "gen": { "height": 1242031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcabdde081e5fa6a873bc145e52d075b8ef84899f4cebc01a16f0ba38e549a27" } } ], "extra": [ 1, 118, 78, 186, 128, 132, 7, 248, 167, 14, 189, 130, 166, 126, 113, 179, 232, 116, 252, 87, 250, 39, 35, 228, 221, 61, 192, 136, 208, 75, 249, 116, 116, 2, 17, 0, 0, 0, 5, 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