Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d6a5dbd9ce671a9159970bf92828b9972a8f4e9ed9ff7e4f798921c83199729

Tx prefix hash: cc0e4370aef2f85325b77778f23fa1728b6480e1aeb80909ec3ba88b08fe4365
Tx public key: f84cd1fb6aaa80fc5ae73057894f5b88eb7261f9930dcd0d90b23328e366e221
Timestamp: 1681667246 Timestamp [UCT]: 2023-04-16 17:47:26 Age [y:d:h:m:s]: 02:218:18:34:26
Block: 739995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676231 RingCT/type: yes/0
Extra: 01f84cd1fb6aaa80fc5ae73057894f5b88eb7261f9930dcd0d90b23328e366e221021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.168151355000 dcy

stealth address amount amount idx
00: df0fadec6cef47ad3bb86f2e24b82790da8cbee3bc64f4172b52236822b74e6b 2.168151355000 1186874 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": 740005, "vin": [ { "gen": { "height": 739995 } } ], "vout": [ { "amount": 2168151355, "target": { "key": "df0fadec6cef47ad3bb86f2e24b82790da8cbee3bc64f4172b52236822b74e6b" } } ], "extra": [ 1, 248, 76, 209, 251, 106, 170, 128, 252, 90, 231, 48, 87, 137, 79, 91, 136, 235, 114, 97, 249, 147, 13, 205, 13, 144, 178, 51, 40, 227, 102, 226, 33, 2, 17, 0, 0, 0, 1, 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