Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e71ab52fdf7a17252e3708c92a04f8006f0102c57842c50a462ee9d6dd5f3d9c

Tx prefix hash: 886eb30749848d7cde35747262c3db86c42c1f2e71ca1121d6ab92489e20f8a9
Tx public key: 54e413435240e9ab1ed32e7b653e0eb2ff89f7356e287eee9f2c2a80f2713376
Timestamp: 1676576056 Timestamp [UCT]: 2023-02-16 19:34:16 Age [y:d:h:m:s]: 02:266:01:32:59
Block: 698441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709464 RingCT/type: yes/0
Extra: 0154e413435240e9ab1ed32e7b653e0eb2ff89f7356e287eee9f2c2a80f27133760211000000028b7b6602000000000000000000

1 output(s) for total of 2.976973344000 dcy

stealth address amount amount idx
00: bf12e55a1a68083554b1ec6082f958938da0b042ac01dac3099be62307818ad4 2.976973344000 1141742 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": 698451, "vin": [ { "gen": { "height": 698441 } } ], "vout": [ { "amount": 2976973344, "target": { "key": "bf12e55a1a68083554b1ec6082f958938da0b042ac01dac3099be62307818ad4" } } ], "extra": [ 1, 84, 228, 19, 67, 82, 64, 233, 171, 30, 211, 46, 123, 101, 62, 14, 178, 255, 137, 247, 53, 110, 40, 126, 238, 159, 44, 42, 128, 242, 113, 51, 118, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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