Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be62d6f56f2b7745ddb5e45442729d2ef060b8acbff2d9b7db9817de2a1946b

Tx prefix hash: 6f692f1bf79e65901164da44b6351d3f781d00c2033d2b52aa55bae61b821ed2
Tx public key: 82c19226ca6ee9ee8bec7913fa857ddcc93f62e1531be14d165252c4b37005c5
Timestamp: 1732882530 Timestamp [UCT]: 2024-11-29 12:15:30 Age [y:d:h:m:s]: 00:115:09:07:56
Block: 1164260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82254 RingCT/type: yes/0
Extra: 0182c19226ca6ee9ee8bec7913fa857ddcc93f62e1531be14d165252c4b37005c50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dae8d82a1c32be61fec90f6a7984b5d1f8db32e7f698599222e8f4d64060b0f 0.600000000000 1649933 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": 1164270, "vin": [ { "gen": { "height": 1164260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dae8d82a1c32be61fec90f6a7984b5d1f8db32e7f698599222e8f4d64060b0f" } } ], "extra": [ 1, 130, 193, 146, 38, 202, 110, 233, 238, 139, 236, 121, 19, 250, 133, 125, 220, 201, 63, 98, 225, 83, 27, 225, 77, 22, 82, 82, 196, 179, 112, 5, 197, 2, 17, 0, 0, 0, 2, 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