Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9384ce486afd3f351e08826766ccaba5e2a581fcbe03aecdb904aa5d2494a4a1

Tx prefix hash: 5a39fb32d4621d9da594721309c2254ed80bab0d786c1b871c35f50da0cadf0a
Tx public key: a823474eed414e0cef04d4ef6bbc083782b931abfc9b150115380e6be0e5762f
Timestamp: 1582340717 Timestamp [UCT]: 2020-02-22 03:05:17 Age [y:d:h:m:s]: 05:081:04:06:39
Block: 70018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211131 RingCT/type: yes/0
Extra: 01a823474eed414e0cef04d4ef6bbc083782b931abfc9b150115380e6be0e5762f02110000000203d36d11000000000000000000

1 output(s) for total of 359.751077849000 dcy

stealth address amount amount idx
00: 54a0f0ce879371dde5f821f6b4cf2cdf8ac0c30f4045d4fc16da0384f1e9bf63 359.751077849000 129198 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": 70028, "vin": [ { "gen": { "height": 70018 } } ], "vout": [ { "amount": 359751077849, "target": { "key": "54a0f0ce879371dde5f821f6b4cf2cdf8ac0c30f4045d4fc16da0384f1e9bf63" } } ], "extra": [ 1, 168, 35, 71, 78, 237, 65, 78, 12, 239, 4, 212, 239, 107, 188, 8, 55, 130, 185, 49, 171, 252, 155, 21, 1, 21, 56, 14, 107, 224, 229, 118, 47, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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