Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f630589553599911140656b2aab8b30933acb1778f2b82ffe4e68da33c625f

Tx prefix hash: 997be96abbea8321322edeed3cd6339ddf7417e2d157067bdfb57391d411ea26
Tx public key: 0cf921f7b936a8fc6caf22fd94645cad3973c36ba1b162a27aa331638d28ec74
Timestamp: 1699741415 Timestamp [UCT]: 2023-11-11 22:23:35 Age [y:d:h:m:s]: 01:140:21:36:02
Block: 889605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361882 RingCT/type: yes/0
Extra: 010cf921f7b936a8fc6caf22fd94645cad3973c36ba1b162a27aa331638d28ec740211000000014b8f5122000000000000000000

1 output(s) for total of 0.692419581000 dcy

stealth address amount amount idx
00: 1eeb88cd9a0d158b4da02c3742001f4c300d5a7844a2c3b4c1995296f5aa0b35 0.692419581000 1345610 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": 889615, "vin": [ { "gen": { "height": 889605 } } ], "vout": [ { "amount": 692419581, "target": { "key": "1eeb88cd9a0d158b4da02c3742001f4c300d5a7844a2c3b4c1995296f5aa0b35" } } ], "extra": [ 1, 12, 249, 33, 247, 185, 54, 168, 252, 108, 175, 34, 253, 148, 100, 92, 173, 57, 115, 195, 107, 161, 177, 98, 162, 122, 163, 49, 99, 141, 40, 236, 116, 2, 17, 0, 0, 0, 1, 75, 143, 81, 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