Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c80ea6871e0427882f28c6487bfd853e653c413111265a23f831b7677ba5039

Tx prefix hash: c1e4ff39a27aa7dc34cc837f274a0e9e826a566578943654cf52492d5ac4c12c
Tx public key: ebfb2261d5a9afd7f4912cae3abe4a028867b47f98b47b726fb129ef03b965a8
Timestamp: 1708063744 Timestamp [UCT]: 2024-02-16 06:09:04 Age [y:d:h:m:s]: 01:049:13:03:24
Block: 958590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296441 RingCT/type: yes/0
Extra: 01ebfb2261d5a9afd7f4912cae3abe4a028867b47f98b47b726fb129ef03b965a802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 262d21d0833406291e1a37f18bee7f91ea45707864f75521212a799e47dfb415 0.600000000000 1417949 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": 958600, "vin": [ { "gen": { "height": 958590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "262d21d0833406291e1a37f18bee7f91ea45707864f75521212a799e47dfb415" } } ], "extra": [ 1, 235, 251, 34, 97, 213, 169, 175, 215, 244, 145, 44, 174, 58, 190, 74, 2, 136, 103, 180, 127, 152, 180, 123, 114, 111, 177, 41, 239, 3, 185, 101, 168, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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