Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e697a77f4ec348abf3c1984e7e03587f85fde3d730aa64e031e3737b66ac65c9

Tx prefix hash: b63d32c6cff47877360357aa7e14c492322b5fc7195cc3f0211e18bd3eda6c3a
Tx public key: 9f66206204fa539b5cd21c2ccc7fb44d16207f72d83601d4bdda9f2dd0842203
Timestamp: 1734466465 Timestamp [UCT]: 2024-12-17 20:14:25 Age [y:d:h:m:s]: 00:022:18:33:26
Block: 1177402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16260 RingCT/type: yes/0
Extra: 019f66206204fa539b5cd21c2ccc7fb44d16207f72d83601d4bdda9f2dd0842203021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d5f24a875b25f49f13c64c458cd00f0e8d324286d8de9aaf5836a21dd43d15 0.600000000000 1663773 of 15

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": 1177412, "vin": [ { "gen": { "height": 1177402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d5f24a875b25f49f13c64c458cd00f0e8d324286d8de9aaf5836a21dd43d15" } } ], "extra": [ 1, 159, 102, 32, 98, 4, 250, 83, 155, 92, 210, 28, 44, 204, 127, 180, 77, 22, 32, 127, 114, 216, 54, 1, 212, 189, 218, 159, 45, 208, 132, 34, 3, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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