Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7672def2b11b16ad390fcf9dd389b7a552b0d13087171a71c23a7c07003ba026

Tx prefix hash: 7ee2c70accdb4e5885677b6b6e9b16b70deb2da7c94749f9d799606845e49d93
Tx public key: adb27357dc770e057fc1460d79f5afd56e0dd75b93c4f0b8ba7d8edbe367220c
Timestamp: 1732334431 Timestamp [UCT]: 2024-11-23 04:00:31 Age [y:d:h:m:s]: 00:212:11:17:03
Block: 1159707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151495 RingCT/type: yes/0
Extra: 01adb27357dc770e057fc1460d79f5afd56e0dd75b93c4f0b8ba7d8edbe367220c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7fcc96549a22a5ca33d8d1ce191cd0b7f9396f26cd27d157b4e9102f0d62a7 0.600000000000 1645346 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": 1159717, "vin": [ { "gen": { "height": 1159707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7fcc96549a22a5ca33d8d1ce191cd0b7f9396f26cd27d157b4e9102f0d62a7" } } ], "extra": [ 1, 173, 178, 115, 87, 220, 119, 14, 5, 127, 193, 70, 13, 121, 245, 175, 213, 110, 13, 215, 91, 147, 196, 240, 184, 186, 125, 142, 219, 227, 103, 34, 12, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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