Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b856d716e071a0a618d939ea12c8bfa1b4444e8396a272151fcbf287b14be2cc

Tx prefix hash: 2a6930b44a0d8a9f5c52f372ba29ae501ef1650e4b31c1afa4297e069e011a9e
Tx public key: aa5474e57295e39c3bbaa4b46786bfd34b3ce01dcfa4e7a871ec1fcba62c28c0
Timestamp: 1690752249 Timestamp [UCT]: 2023-07-30 21:24:09 Age [y:d:h:m:s]: 01:311:05:13:13
Block: 815343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483555 RingCT/type: yes/0
Extra: 01aa5474e57295e39c3bbaa4b46786bfd34b3ce01dcfa4e7a871ec1fcba62c28c002110000000475e3f0e9000000000000000000

1 output(s) for total of 1.220197929000 dcy

stealth address amount amount idx
00: 95260b5b3d7e93104a64f98b0f3794a9ea1844768078cdfefd224b386a9b68fd 1.220197929000 1267140 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": 815353, "vin": [ { "gen": { "height": 815343 } } ], "vout": [ { "amount": 1220197929, "target": { "key": "95260b5b3d7e93104a64f98b0f3794a9ea1844768078cdfefd224b386a9b68fd" } } ], "extra": [ 1, 170, 84, 116, 229, 114, 149, 227, 156, 59, 186, 164, 180, 103, 134, 191, 211, 75, 60, 224, 29, 207, 164, 231, 168, 113, 236, 31, 203, 166, 44, 40, 192, 2, 17, 0, 0, 0, 4, 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