Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8388ddaa57d51feb410f09d4b6614e94672d0f80b7a222bf21e0a5da242a97b1

Tx prefix hash: 91d3a4a0f1e6251c6084e7db56031ee160e13b91cec8b3755ea0673e4fe57d1b
Tx public key: 1d28af1122c56d2ea775ff0a89340e0459ee2ea7d5b5026e362a68cc7bb57a1f
Timestamp: 1582917914 Timestamp [UCT]: 2020-02-28 19:25:14 Age [y:d:h:m:s]: 05:075:06:03:43
Block: 73582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1208109 RingCT/type: yes/0
Extra: 011d28af1122c56d2ea775ff0a89340e0459ee2ea7d5b5026e362a68cc7bb57a1f0211000000098a2ee0d9000000000000000000

1 output(s) for total of 350.100787791000 dcy

stealth address amount amount idx
00: db019684df980b973ad5cd6d8aa3c5fc487f7aadab54e9c741b74236ddf6a20b 350.100787791000 135777 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": 73592, "vin": [ { "gen": { "height": 73582 } } ], "vout": [ { "amount": 350100787791, "target": { "key": "db019684df980b973ad5cd6d8aa3c5fc487f7aadab54e9c741b74236ddf6a20b" } } ], "extra": [ 1, 29, 40, 175, 17, 34, 197, 109, 46, 167, 117, 255, 10, 137, 52, 14, 4, 89, 238, 46, 167, 213, 181, 2, 110, 54, 42, 104, 204, 123, 181, 122, 31, 2, 17, 0, 0, 0, 9, 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