Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 261a59dde7c3980b0c3c8b2b97bff510faf12dbb74c52e0e71d5788bcb412a95

Tx prefix hash: 878188d443956f397de699130698c0ba40b387d0d024865f1ee2f484bc432f0e
Tx public key: 17f1ee090ce6d55ec380e70fb313b9648d19bcaa75fce8616a92a0dab4fe98a5
Timestamp: 1582439277 Timestamp [UCT]: 2020-02-23 06:27:57 Age [y:d:h:m:s]: 05:017:17:55:04
Block: 70749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165862 RingCT/type: yes/0
Extra: 0117f1ee090ce6d55ec380e70fb313b9648d19bcaa75fce8616a92a0dab4fe98a5021100000001724f989b000000000000000000

1 output(s) for total of 357.750291478000 dcy

stealth address amount amount idx
00: 589c0ab3e5f527dac0f54faaa49147484430b331dffa21cdd3067eb60cb0d52e 357.750291478000 130701 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": 70759, "vin": [ { "gen": { "height": 70749 } } ], "vout": [ { "amount": 357750291478, "target": { "key": "589c0ab3e5f527dac0f54faaa49147484430b331dffa21cdd3067eb60cb0d52e" } } ], "extra": [ 1, 23, 241, 238, 9, 12, 230, 213, 94, 195, 128, 231, 15, 179, 19, 185, 100, 141, 25, 188, 170, 117, 252, 232, 97, 106, 146, 160, 218, 180, 254, 152, 165, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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