Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9a363484af88f03b390bded69281d2a806dd172931a795629b89ba3eb4cd9a1

Tx prefix hash: e4cfb0319ebed792016e261c31fb902a4e418fe7ea56cabf7472501fd0c3b4e4
Tx public key: 0947a2bd25e32dddee54a012dd1a1ed54ae5404ee0128d11ee291039249c6265
Timestamp: 1581704926 Timestamp [UCT]: 2020-02-14 18:28:46 Age [y:d:h:m:s]: 05:115:18:12:43
Block: 65314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235322 RingCT/type: yes/0
Extra: 010947a2bd25e32dddee54a012dd1a1ed54ae5404ee0128d11ee291039249c6265021100000002724f989b000000000000000000

1 output(s) for total of 372.896593001000 dcy

stealth address amount amount idx
00: 0eb8a2cb8354bcf192a0c32ef3cfcc43b26fb2514068be38b0d1727ad1edec5e 372.896593001000 120357 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": 65324, "vin": [ { "gen": { "height": 65314 } } ], "vout": [ { "amount": 372896593001, "target": { "key": "0eb8a2cb8354bcf192a0c32ef3cfcc43b26fb2514068be38b0d1727ad1edec5e" } } ], "extra": [ 1, 9, 71, 162, 189, 37, 227, 45, 221, 238, 84, 160, 18, 221, 26, 30, 213, 74, 229, 64, 78, 224, 18, 141, 17, 238, 41, 16, 57, 36, 156, 98, 101, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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