Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87763641fcd091b665d6828113b7c6bc42e6c858aad2e7afe492d83a277d229c

Tx prefix hash: 00d049a5e9e009a4621d567f5d3731d8d9ddce5a4ffb85aa0d27b40124a9518f
Tx public key: b00bbeed66b3b1f5ba9adc3d96bd58952e696d21a34bec0d17e143a2bb47dd66
Timestamp: 1729275510 Timestamp [UCT]: 2024-10-18 18:18:30 Age [y:d:h:m:s]: 00:146:20:58:42
Block: 1134462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104742 RingCT/type: yes/0
Extra: 01b00bbeed66b3b1f5ba9adc3d96bd58952e696d21a34bec0d17e143a2bb47dd660211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce20e559f2d03ef082ef0c9dc4b7f9b6f4c4d92f656afa55e0ef564ec6866f5f 0.600000000000 1617769 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": 1134472, "vin": [ { "gen": { "height": 1134462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce20e559f2d03ef082ef0c9dc4b7f9b6f4c4d92f656afa55e0ef564ec6866f5f" } } ], "extra": [ 1, 176, 11, 190, 237, 102, 179, 177, 245, 186, 154, 220, 61, 150, 189, 88, 149, 46, 105, 109, 33, 163, 75, 236, 13, 23, 225, 67, 162, 187, 71, 221, 102, 2, 17, 0, 0, 0, 3, 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