Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2005169d22036a1132b1f02e6bd02d3033ef35bb77385c0f5c8d5c09e29ee6d

Tx prefix hash: 5ce34719394871b587dc4b5758c606557660d8ba3978f0dddeb71d18bc81a89a
Tx public key: 8477f730df72a54cb53d92febd860c9a4c52d22aabce53e62d237fb573a56152
Timestamp: 1699665049 Timestamp [UCT]: 2023-11-11 01:10:49 Age [y:d:h:m:s]: 01:139:16:55:12
Block: 888980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361023 RingCT/type: yes/0
Extra: 018477f730df72a54cb53d92febd860c9a4c52d22aabce53e62d237fb573a56152021100000004faf35c9c000000000000000000

1 output(s) for total of 0.695729192000 dcy

stealth address amount amount idx
00: cc4e149a9b4a5b329270162353cd214cfb77568b0e6eb6970c9bfa1299875597 0.695729192000 1344949 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": 888990, "vin": [ { "gen": { "height": 888980 } } ], "vout": [ { "amount": 695729192, "target": { "key": "cc4e149a9b4a5b329270162353cd214cfb77568b0e6eb6970c9bfa1299875597" } } ], "extra": [ 1, 132, 119, 247, 48, 223, 114, 165, 76, 181, 61, 146, 254, 189, 134, 12, 154, 76, 82, 210, 42, 171, 206, 83, 230, 45, 35, 127, 181, 115, 165, 97, 82, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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