Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5551c69d638200f17ffbaddb47930ad3c5bef9957e3ae1aad0c8f4fd8a276d28

Tx prefix hash: abff0861cb89783181a19222a334e4265e889127bc464d853419f33bcc3cef12
Tx public key: fd2ab3efd487f577458df52ff8521dc6de0e8d55d4177e4170cddf8c0b7187b4
Timestamp: 1696554134 Timestamp [UCT]: 2023-10-06 01:02:14 Age [y:d:h:m:s]: 01:179:18:04:55
Block: 863374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389515 RingCT/type: yes/0
Extra: 01fd2ab3efd487f577458df52ff8521dc6de0e8d55d4177e4170cddf8c0b7187b4021100000007faf35c9c000000000000000000

1 output(s) for total of 0.845830948000 dcy

stealth address amount amount idx
00: 8281eafa565ddd7327eb652eafc435fce9da55ca0614eebb51425c0f74a95e90 0.845830948000 1317826 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": 863384, "vin": [ { "gen": { "height": 863374 } } ], "vout": [ { "amount": 845830948, "target": { "key": "8281eafa565ddd7327eb652eafc435fce9da55ca0614eebb51425c0f74a95e90" } } ], "extra": [ 1, 253, 42, 179, 239, 212, 135, 245, 119, 69, 141, 245, 47, 248, 82, 29, 198, 222, 14, 141, 85, 212, 23, 126, 65, 112, 205, 223, 140, 11, 113, 135, 180, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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