Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfd49867b0e9a0b3146b1b0c220ebc0cc80a88b212075bcac1a5eae8f6c48f42

Tx prefix hash: b0320b793e4d107ef0268539e5f408cf9a88c1cd9d6c101f39c517efcf5e7c5f
Tx public key: ff240d0e11a87fec413fa3325cea4903b7d24bce1e1f834fabec95195490bb72
Timestamp: 1702704542 Timestamp [UCT]: 2023-12-16 05:29:02 Age [y:d:h:m:s]: 02:026:13:11:02
Block: 914170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538786 RingCT/type: yes/0
Extra: 01ff240d0e11a87fec413fa3325cea4903b7d24bce1e1f834fabec95195490bb72021100000012e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 701c02c14a9e24b3362c0d3b36b4c8d64e17d479777fa389982d3b39b5c09968 0.600000000000 1371456 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": 914180, "vin": [ { "gen": { "height": 914170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "701c02c14a9e24b3362c0d3b36b4c8d64e17d479777fa389982d3b39b5c09968" } } ], "extra": [ 1, 255, 36, 13, 14, 17, 168, 127, 236, 65, 63, 163, 50, 92, 234, 73, 3, 183, 210, 75, 206, 30, 31, 131, 79, 171, 236, 149, 25, 84, 144, 187, 114, 2, 17, 0, 0, 0, 18, 230, 210, 127, 156, 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