Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a15ba216f1fcf1f7b242f64e8316495fcc4953a491ebd841bd1ea26631cbe55a

Tx prefix hash: f174946cf8fa885c44eaa37e49577765d9d155b333bc10fd43ee5d16ea1aa769
Tx public key: 029c44c19deb15af1fa5f250424c91b40676b8062d18cb1e2e2577b74b7bf12e
Timestamp: 1710915233 Timestamp [UCT]: 2024-03-20 06:13:53 Age [y:d:h:m:s]: 00:342:00:24:21
Block: 982257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244494 RingCT/type: yes/0
Extra: 01029c44c19deb15af1fa5f250424c91b40676b8062d18cb1e2e2577b74b7bf12e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57c6ab927f69da16e3aa37d4d6b573105de92c4121afb1db474fec42b33e10f5 0.600000000000 1442362 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": 982267, "vin": [ { "gen": { "height": 982257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57c6ab927f69da16e3aa37d4d6b573105de92c4121afb1db474fec42b33e10f5" } } ], "extra": [ 1, 2, 156, 68, 193, 157, 235, 21, 175, 31, 165, 242, 80, 66, 76, 145, 180, 6, 118, 184, 6, 45, 24, 203, 30, 46, 37, 119, 183, 75, 123, 241, 46, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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