Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092875369305ee1a93ad5103efdd8b2291a8e8ecf1dbda850ea97d65b3e5e74c

Tx prefix hash: 4ab98c24e1c169ceea1db5a518dcae7a5c2d6bf4af483605d440b1347247df0e
Tx public key: aa1b9f2352f8947519074f8143a546de2058cfb813db85f1cacaa93e83fdda1f
Timestamp: 1583072287 Timestamp [UCT]: 2020-03-01 14:18:07 Age [y:d:h:m:s]: 05:222:19:53:42
Block: 74489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1311603 RingCT/type: yes/0
Extra: 01aa1b9f2352f8947519074f8143a546de2058cfb813db85f1cacaa93e83fdda1f0211000000a87adf42d3000000000000000000

1 output(s) for total of 347.686492777000 dcy

stealth address amount amount idx
00: f173cae7e6dfc712acc7fdca65e517d2c6dd55c7d519a9890290ce525988187e 347.686492777000 137852 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": 74499, "vin": [ { "gen": { "height": 74489 } } ], "vout": [ { "amount": 347686492777, "target": { "key": "f173cae7e6dfc712acc7fdca65e517d2c6dd55c7d519a9890290ce525988187e" } } ], "extra": [ 1, 170, 27, 159, 35, 82, 248, 148, 117, 25, 7, 79, 129, 67, 165, 70, 222, 32, 88, 207, 184, 19, 219, 133, 241, 202, 202, 169, 62, 131, 253, 218, 31, 2, 17, 0, 0, 0, 168, 122, 223, 66, 211, 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