Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fa96d5dd338648606e8c86df4c79267baf95d24659b3772b91ce98bec69c0fc

Tx prefix hash: 8388231f4be06a1fddcd58193feff125c2917709faf16255cf3326fbba85cf5c
Tx public key: 0dd0363dd5725ad2b2f50e7958af3558d86da540468bc0d6a4301d3fe7a62f5f
Timestamp: 1676423678 Timestamp [UCT]: 2023-02-15 01:14:38 Age [y:d:h:m:s]: 02:063:04:23:18
Block: 697173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566762 RingCT/type: yes/0
Extra: 010dd0363dd5725ad2b2f50e7958af3558d86da540468bc0d6a4301d3fe7a62f5f021100000002835e4d22000000000000000000

1 output(s) for total of 3.005912664000 dcy

stealth address amount amount idx
00: 914706aa0f96ca78ae7450c0ba283c4bd0b6a55d6d92d5ae262412f40028a5d9 3.005912664000 1140292 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": 697183, "vin": [ { "gen": { "height": 697173 } } ], "vout": [ { "amount": 3005912664, "target": { "key": "914706aa0f96ca78ae7450c0ba283c4bd0b6a55d6d92d5ae262412f40028a5d9" } } ], "extra": [ 1, 13, 208, 54, 61, 213, 114, 90, 210, 178, 245, 14, 121, 88, 175, 53, 88, 216, 109, 165, 64, 70, 139, 192, 214, 164, 48, 29, 63, 231, 166, 47, 95, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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