Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a039735b0dec11b038dfb7735118883b522de15709d73df7c4068eceb7067246

Tx prefix hash: b4649bc71aaaccfc6b366eda6591c6ff2c3867e5ec6fcf4a71488153c4740f3c
Tx public key: 8e27c29580a30ebb5d7bef3025a5ae5861b38dcbeb6accbb86776291ac9cb612
Timestamp: 1733244639 Timestamp [UCT]: 2024-12-03 16:50:39 Age [y:d:h:m:s]: 00:142:22:49:54
Block: 1167266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101981 RingCT/type: yes/0
Extra: 018e27c29580a30ebb5d7bef3025a5ae5861b38dcbeb6accbb86776291ac9cb6120211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527fa0b4e0f10d4cc63cb2eb5c69c19cbaea4553037eeae49ed6f7a3e344ab2e 0.600000000000 1652961 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": 1167276, "vin": [ { "gen": { "height": 1167266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527fa0b4e0f10d4cc63cb2eb5c69c19cbaea4553037eeae49ed6f7a3e344ab2e" } } ], "extra": [ 1, 142, 39, 194, 149, 128, 163, 14, 187, 93, 123, 239, 48, 37, 165, 174, 88, 97, 179, 141, 203, 235, 106, 204, 187, 134, 119, 98, 145, 172, 156, 182, 18, 2, 17, 0, 0, 0, 4, 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