Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 038c6d6aa21261a748aeaf8642e9daf47e11aac1af2478af489d7075e02f5579

Tx prefix hash: 27754fe43afd676cd64f1a4e5fd4b9138bd638c76af9c4c40623de5cb1abfe26
Tx public key: 8a894e47d67ed6beca36a8c2d69a9bd56d9d6671110e95e7b934cb4fee8d84d4
Timestamp: 1581090191 Timestamp [UCT]: 2020-02-07 15:43:11 Age [y:d:h:m:s]: 04:330:04:58:13
Block: 60617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127494 RingCT/type: yes/0
Extra: 018a894e47d67ed6beca36a8c2d69a9bd56d9d6671110e95e7b934cb4fee8d84d40211000000030aca7173000000000000000000

1 output(s) for total of 386.501810925000 dcy

stealth address amount amount idx
00: 9fec9605a732243305d83d5ed41534c34d552f57702dfbca949a0d5e970e0c3a 386.501810925000 111639 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": 60627, "vin": [ { "gen": { "height": 60617 } } ], "vout": [ { "amount": 386501810925, "target": { "key": "9fec9605a732243305d83d5ed41534c34d552f57702dfbca949a0d5e970e0c3a" } } ], "extra": [ 1, 138, 137, 78, 71, 214, 126, 214, 190, 202, 54, 168, 194, 214, 154, 155, 213, 109, 157, 102, 113, 17, 14, 149, 231, 185, 52, 203, 79, 238, 141, 132, 212, 2, 17, 0, 0, 0, 3, 10, 202, 113, 115, 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