Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5715e1399bae90165b4635546cd1ec20fe0f6cb2630cd637c303afd7837cce3

Tx prefix hash: 35a0a8dfed9972c9301f704fcab765db2fa17fa95d8d4c48cd8337484c61606c
Tx public key: e710acd7d8a2e0860d95b4c3657df44e7cb1e5ebb8e04ac9924cfa37f630eeb1
Timestamp: 1577664017 Timestamp [UCT]: 2019-12-30 00:00:17 Age [y:d:h:m:s]: 04:327:08:49:27
Block: 34634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123073 RingCT/type: yes/0
Extra: 01e710acd7d8a2e0860d95b4c3657df44e7cb1e5ebb8e04ac9924cfa37f630eeb1021100000004d81c26c0000000000000000000

1 output(s) for total of 471.250169615000 dcy

stealth address amount amount idx
00: 39c0cd18c31c6eba41f0c1ffaeb7b4f1f8ed627d395b99b9122f1f69d6f98c4f 471.250169615000 58314 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": 34644, "vin": [ { "gen": { "height": 34634 } } ], "vout": [ { "amount": 471250169615, "target": { "key": "39c0cd18c31c6eba41f0c1ffaeb7b4f1f8ed627d395b99b9122f1f69d6f98c4f" } } ], "extra": [ 1, 231, 16, 172, 215, 216, 162, 224, 134, 13, 149, 180, 195, 101, 125, 244, 78, 124, 177, 229, 235, 184, 224, 74, 201, 146, 76, 250, 55, 246, 48, 238, 177, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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