Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04a7fd0f81513e255e2a7982b77337e7cb986fdd7df44c812c2c4edb96d47a6f

Tx prefix hash: 896a97838a62be1f3f95341984f0f08b154af7b16f79359e7f75a43c83029cd0
Tx public key: de9dbccd0caee5c95c65647df1c261b3aca216ad292568264f8aa68fc9810f99
Timestamp: 1724812022 Timestamp [UCT]: 2024-08-28 02:27:02 Age [y:d:h:m:s]: 00:178:19:57:59
Block: 1097439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127635 RingCT/type: yes/0
Extra: 01de9dbccd0caee5c95c65647df1c261b3aca216ad292568264f8aa68fc9810f9902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bbfdb08754cdbf4cdfe3362a275a7d0856938a7054e32b65b7e6496adaf952b 0.600000000000 1572836 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": 1097449, "vin": [ { "gen": { "height": 1097439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bbfdb08754cdbf4cdfe3362a275a7d0856938a7054e32b65b7e6496adaf952b" } } ], "extra": [ 1, 222, 157, 188, 205, 12, 174, 229, 201, 92, 101, 100, 125, 241, 194, 97, 179, 172, 162, 22, 173, 41, 37, 104, 38, 79, 138, 166, 143, 201, 129, 15, 153, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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