Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f54cbc41bb979e3ac8ce312ddf92faa926e7f3297a2ca2b707881ed943e44fd

Tx prefix hash: 9c9ba1825b17a27257dd37652e8db457fe9bbc6d94f7658893192eb83a44e7a1
Tx public key: fa9ac55457c8a18b43fd3a94cafdb3a253163390ccf4315a07ca5ae09ee5aed9
Timestamp: 1581083215 Timestamp [UCT]: 2020-02-07 13:46:55 Age [y:d:h:m:s]: 04:292:20:12:12
Block: 60204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101124 RingCT/type: yes/0
Extra: 01fa9ac55457c8a18b43fd3a94cafdb3a253163390ccf4315a07ca5ae09ee5aed90211000000027adf42d3000000000000000000

1 output(s) for total of 387.721580272000 dcy

stealth address amount amount idx
00: 39776ecc50d4802cf469a347ea84408953001e0ecf7461f132d3924fbb479612 387.721580272000 111054 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": 60214, "vin": [ { "gen": { "height": 60204 } } ], "vout": [ { "amount": 387721580272, "target": { "key": "39776ecc50d4802cf469a347ea84408953001e0ecf7461f132d3924fbb479612" } } ], "extra": [ 1, 250, 154, 197, 84, 87, 200, 161, 139, 67, 253, 58, 148, 202, 253, 179, 162, 83, 22, 51, 144, 204, 244, 49, 90, 7, 202, 90, 224, 158, 229, 174, 217, 2, 17, 0, 0, 0, 2, 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