Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a16311c251fe8a2fd771e7f0d2bbe688fe100056841717508d1863e8cd1ee44

Tx prefix hash: 40696ad00f3a6dd2d36a7c6f3d5ffa22154f3e4fe696e21de43559c98910c52f
Tx public key: a5f5d8866fb3536d12f9742ddea12567237a8ae4da12ff5c770ac218b3de21af
Timestamp: 1692311321 Timestamp [UCT]: 2023-08-17 22:28:41 Age [y:d:h:m:s]: 01:279:02:16:02
Block: 828164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460678 RingCT/type: yes/0
Extra: 01a5f5d8866fb3536d12f9742ddea12567237a8ae4da12ff5c770ac218b3de21af02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.106493761000 dcy

stealth address amount amount idx
00: 74a56f4ba4b03a9c699c481b0bb4946bcb54d6446c0d1db9882b3c15d9f2ffbe 1.106493761000 1280484 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": 828174, "vin": [ { "gen": { "height": 828164 } } ], "vout": [ { "amount": 1106493761, "target": { "key": "74a56f4ba4b03a9c699c481b0bb4946bcb54d6446c0d1db9882b3c15d9f2ffbe" } } ], "extra": [ 1, 165, 245, 216, 134, 111, 179, 83, 109, 18, 249, 116, 45, 222, 161, 37, 103, 35, 122, 138, 228, 218, 18, 255, 92, 119, 10, 194, 24, 179, 222, 33, 175, 2, 17, 0, 0, 0, 3, 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