Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33bdd27925e9999f85a420152eb34c4f5ce9bf9a719d5fa335f7e469175f9acc

Tx prefix hash: 08dd94e8ede899b6c69d6cdc8da7ee5258a3b735a64c10d17601a5b9f3192447
Tx public key: ca0527e6b0d5323c52a539a016128acf876026e2884ff7c9fe7b2e1db86fd64d
Timestamp: 1673791228 Timestamp [UCT]: 2023-01-15 14:00:28 Age [y:d:h:m:s]: 02:082:18:57:31
Block: 675321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580836 RingCT/type: yes/0
Extra: 01ca0527e6b0d5323c52a539a016128acf876026e2884ff7c9fe7b2e1db86fd64d021100000002044c7254000000000000000000

1 output(s) for total of 3.551249106000 dcy

stealth address amount amount idx
00: 4c7f0fbe0da60f4bf6a93c0648d9e749d13829507dee85b85e77dad32de8a116 3.551249106000 1116996 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": 675331, "vin": [ { "gen": { "height": 675321 } } ], "vout": [ { "amount": 3551249106, "target": { "key": "4c7f0fbe0da60f4bf6a93c0648d9e749d13829507dee85b85e77dad32de8a116" } } ], "extra": [ 1, 202, 5, 39, 230, 176, 213, 50, 60, 82, 165, 57, 160, 22, 18, 138, 207, 135, 96, 38, 226, 136, 79, 247, 201, 254, 123, 46, 29, 184, 111, 214, 77, 2, 17, 0, 0, 0, 2, 4, 76, 114, 84, 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