Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd05d2164eb93664078dc751e457ab57c4f237d28178af241b08536c99f83a7d

Tx prefix hash: 8e365051765ae150024052ba057d1398da92238a29665582822e9e3acc7c347a
Tx public key: e0759f9a294975f5c01d8ccac4271a1b3d6d3017f9e28bf421e0d12996726af3
Timestamp: 1581939630 Timestamp [UCT]: 2020-02-17 11:40:30 Age [y:d:h:m:s]: 04:323:16:35:59
Block: 66585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123912 RingCT/type: yes/0
Extra: 01e0759f9a294975f5c01d8ccac4271a1b3d6d3017f9e28bf421e0d12996726af30211000000058a2ee0d9000000000000000000

1 output(s) for total of 369.302441222000 dcy

stealth address amount amount idx
00: 5b88c9ca8cb05190534818a2bc4a53f522cb5a7de2da117db52d6fa9aef55d19 369.302441222000 122688 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": 66595, "vin": [ { "gen": { "height": 66585 } } ], "vout": [ { "amount": 369302441222, "target": { "key": "5b88c9ca8cb05190534818a2bc4a53f522cb5a7de2da117db52d6fa9aef55d19" } } ], "extra": [ 1, 224, 117, 159, 154, 41, 73, 117, 245, 192, 29, 140, 202, 196, 39, 26, 27, 61, 109, 48, 23, 249, 226, 139, 244, 33, 224, 209, 41, 150, 114, 106, 243, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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