Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c69e991908d43209cd76ad887daacc557d749aca4ca55893e2f8840925b9d0

Tx prefix hash: 1248eabd5348b96bbe589ce45f1cee838d78f90185fe69ad9f93467700a37d1c
Tx public key: 7dd5d6fd090c9e0b6766d84d890f2af4e562bc997c9c5f39cb24bf0c4e03982a
Timestamp: 1582501021 Timestamp [UCT]: 2020-02-23 23:37:01 Age [y:d:h:m:s]: 04:304:20:17:06
Block: 70983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110726 RingCT/type: yes/0
Extra: 017dd5d6fd090c9e0b6766d84d890f2af4e562bc997c9c5f39cb24bf0c4e03982a02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 357.134874982000 dcy

stealth address amount amount idx
00: 1eeecc3b3cf29e4a3a67c7c6150db7a589af653fa2f44df2c08e26465e12e8d3 357.134874982000 131222 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": 70993, "vin": [ { "gen": { "height": 70983 } } ], "vout": [ { "amount": 357134874982, "target": { "key": "1eeecc3b3cf29e4a3a67c7c6150db7a589af653fa2f44df2c08e26465e12e8d3" } } ], "extra": [ 1, 125, 213, 214, 253, 9, 12, 158, 11, 103, 102, 216, 77, 137, 15, 42, 244, 229, 98, 188, 153, 124, 156, 95, 57, 203, 36, 191, 12, 78, 3, 152, 42, 2, 17, 0, 0, 0, 11, 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