Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5de06d56e5e4c0e7147de047f37b234c49604622e3cea1e1f167e236b1595677

Tx prefix hash: 421d4d25c8c6c50dcb15a8da58a11d9611c54838fe683dbe3ba9d9c3fe657fd5
Tx public key: cea84dc53d914422ebbfcb2a136d2461da79d9b4a113373d2eef34a0260c2602
Timestamp: 1723606317 Timestamp [UCT]: 2024-08-14 03:31:57 Age [y:d:h:m:s]: 00:238:15:07:14
Block: 1087453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170426 RingCT/type: yes/0
Extra: 01cea84dc53d914422ebbfcb2a136d2461da79d9b4a113373d2eef34a0260c2602021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a52e04535f962c328a805d610ba1c92cb40431581197c5b2aec61f261482a073 0.600000000000 1562062 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": 1087463, "vin": [ { "gen": { "height": 1087453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a52e04535f962c328a805d610ba1c92cb40431581197c5b2aec61f261482a073" } } ], "extra": [ 1, 206, 168, 77, 197, 61, 145, 68, 34, 235, 191, 203, 42, 19, 109, 36, 97, 218, 121, 217, 180, 161, 19, 55, 61, 46, 239, 52, 160, 38, 12, 38, 2, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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