Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2ba4c9c161c2652be23404c0335856f559e783718655e029465b1dd28328ce1

Tx prefix hash: 394657aa1c937274cc0aa954a1152374d41bc7b8510da8b61b8d41a329ab998d
Tx public key: 532f0fd158768e34a01bb1374df32b9c5c8331be47c785dc186b9c9486e96244
Timestamp: 1696126140 Timestamp [UCT]: 2023-10-01 02:09:00 Age [y:d:h:m:s]: 02:042:07:22:05
Block: 859831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549877 RingCT/type: yes/0
Extra: 01532f0fd158768e34a01bb1374df32b9c5c8331be47c785dc186b9c9486e9624402110000000333af99f4000000000000000000

1 output(s) for total of 0.869006463000 dcy

stealth address amount amount idx
00: f18a2193f73a2628faea557a45e3bb10ab52c5098cd7736523ace108b8d5088c 0.869006463000 1314079 of 0

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": 859841, "vin": [ { "gen": { "height": 859831 } } ], "vout": [ { "amount": 869006463, "target": { "key": "f18a2193f73a2628faea557a45e3bb10ab52c5098cd7736523ace108b8d5088c" } } ], "extra": [ 1, 83, 47, 15, 209, 88, 118, 142, 52, 160, 27, 177, 55, 77, 243, 43, 156, 92, 131, 49, 190, 71, 199, 133, 220, 24, 107, 156, 148, 134, 233, 98, 68, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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