Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dcf9ab183c75e45ab849d62f7faf3241bef1c59d5bc0e63251fe94147b9a758

Tx prefix hash: bf83f1bb371abd2cc84b6abcf94a61380ca2ab7e30eeb2c0a4779d0282c5d58e
Tx public key: 2c46ef4d9064c342fddc46f65e9e08989be3f2b13f7716552fd174a287b85cc5
Timestamp: 1714340517 Timestamp [UCT]: 2024-04-28 21:41:57 Age [y:d:h:m:s]: 00:244:05:45:35
Block: 1010630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174820 RingCT/type: yes/0
Extra: 012c46ef4d9064c342fddc46f65e9e08989be3f2b13f7716552fd174a287b85cc502110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b26c65c1cb4ba7bb6f2f92e7bcdf7007045aee5208641be92f757fd6f7174159 0.600000000000 1472640 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": 1010640, "vin": [ { "gen": { "height": 1010630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b26c65c1cb4ba7bb6f2f92e7bcdf7007045aee5208641be92f757fd6f7174159" } } ], "extra": [ 1, 44, 70, 239, 77, 144, 100, 195, 66, 253, 220, 70, 246, 94, 158, 8, 152, 155, 227, 242, 177, 63, 119, 22, 85, 47, 209, 116, 162, 135, 184, 92, 197, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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