Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdec31e87466a7c73287e617466b01a7290459fd4f230f5348b66c4e3d88805e

Tx prefix hash: 59f58f5f0947b793f6a3f8807f940fce6a1f44288fcd72e1794778d363a81edb
Tx public key: 1142c5d9c0f6f74ef16ffe1677d3ec26a5978aea4292617c90170c862669b3b2
Timestamp: 1706307592 Timestamp [UCT]: 2024-01-26 22:19:52 Age [y:d:h:m:s]: 01:073:20:13:44
Block: 944010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313867 RingCT/type: yes/0
Extra: 011142c5d9c0f6f74ef16ffe1677d3ec26a5978aea4292617c90170c862669b3b202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21e5eb2786af8f517958d032690dd51be6abfd1c3fedf1f946132e569dd9467a 0.600000000000 1402236 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": 944020, "vin": [ { "gen": { "height": 944010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21e5eb2786af8f517958d032690dd51be6abfd1c3fedf1f946132e569dd9467a" } } ], "extra": [ 1, 17, 66, 197, 217, 192, 246, 247, 78, 241, 111, 254, 22, 119, 211, 236, 38, 165, 151, 138, 234, 66, 146, 97, 124, 144, 23, 12, 134, 38, 105, 179, 178, 2, 17, 0, 0, 0, 3, 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