Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b42e955ef410555dc7bee86e5ff02f8f6d0e906bd29b0007535739bd41efbe4

Tx prefix hash: d15e94b0ac5a6f61c0726099c70b7bc41edde303a0bd1e8e6e0689b89fc78914
Tx public key: ce17a904dfad32f41f881be5522c9c177ce158b5286d4a8691f3ab0b49688dc9
Timestamp: 1729126264 Timestamp [UCT]: 2024-10-17 00:51:04 Age [y:d:h:m:s]: 00:183:05:17:43
Block: 1133216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130736 RingCT/type: yes/0
Extra: 01ce17a904dfad32f41f881be5522c9c177ce158b5286d4a8691f3ab0b49688dc90211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c74cbfc22bc0c29a9f61759a88a50f8dd510876146415aaa5523f840e44a3229 0.600000000000 1616293 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": 1133226, "vin": [ { "gen": { "height": 1133216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c74cbfc22bc0c29a9f61759a88a50f8dd510876146415aaa5523f840e44a3229" } } ], "extra": [ 1, 206, 23, 169, 4, 223, 173, 50, 244, 31, 136, 27, 229, 82, 44, 156, 23, 124, 225, 88, 181, 40, 109, 74, 134, 145, 243, 171, 11, 73, 104, 141, 201, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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