Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a19768485e9f0e70a59b194e368ba8faa870d4a1eaf713680628e12228aeabf4

Tx prefix hash: 6b49ab186c919c155b650981d9bf1d82fdc090d77e54c6be7d1c2e92a122aa29
Tx public key: a26bfeece9de5e8a99c682705f5a50cb609e398309ab307f4c337d130cbe3793
Timestamp: 1662056934 Timestamp [UCT]: 2022-09-01 18:28:54 Age [y:d:h:m:s]: 02:166:05:40:59
Block: 578678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640037 RingCT/type: yes/0
Extra: 01a26bfeece9de5e8a99c682705f5a50cb609e398309ab307f4c337d130cbe379302110000000175e3f0e9000000000000000000

1 output(s) for total of 7.423345183000 dcy

stealth address amount amount idx
00: 5f19e40511a901294f2017e2cad43106e13f06b4d46dddb630643d1df0e21a55 7.423345183000 1012100 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": 578688, "vin": [ { "gen": { "height": 578678 } } ], "vout": [ { "amount": 7423345183, "target": { "key": "5f19e40511a901294f2017e2cad43106e13f06b4d46dddb630643d1df0e21a55" } } ], "extra": [ 1, 162, 107, 254, 236, 233, 222, 94, 138, 153, 198, 130, 112, 95, 90, 80, 203, 96, 158, 57, 131, 9, 171, 48, 127, 76, 51, 125, 19, 12, 190, 55, 147, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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