Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d549a60d69fff93c02ccf759a32d17db42ca0566473137dd967056d6991d75

Tx prefix hash: ec8da4c854486937b6d6b3c1e6b4284298765bdf13bc81a2aecddfeaad3419ba
Tx public key: ddd5fb73bcc194e0e3f12aee9d29df3f92f0f2238d08b5dd46bc1e8d2faf6d36
Timestamp: 1672903989 Timestamp [UCT]: 2023-01-05 07:33:09 Age [y:d:h:m:s]: 01:332:01:28:42
Block: 667959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498367 RingCT/type: yes/0
Extra: 01ddd5fb73bcc194e0e3f12aee9d29df3f92f0f2238d08b5dd46bc1e8d2faf6d3602110000000152542ceb000000000000000000

1 output(s) for total of 3.756423167000 dcy

stealth address amount amount idx
00: d02be11570806b09afcb0c833d562ae101aac4c40a9987a3d7f7577187f5f6e0 3.756423167000 1109182 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": 667969, "vin": [ { "gen": { "height": 667959 } } ], "vout": [ { "amount": 3756423167, "target": { "key": "d02be11570806b09afcb0c833d562ae101aac4c40a9987a3d7f7577187f5f6e0" } } ], "extra": [ 1, 221, 213, 251, 115, 188, 193, 148, 224, 227, 241, 42, 238, 157, 41, 223, 63, 146, 240, 242, 35, 141, 8, 181, 221, 70, 188, 30, 141, 47, 175, 109, 54, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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