Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 337b9277f92e96dc26c7e92194bc81a41a294f342d6aa6ba145a979f291c5f29

Tx prefix hash: 1941dc172c0a5efd6fd5e0eafdbd6d3093930f2f3966bbf918d13ebdaa0fc99d
Tx public key: 18c45d6de84c980b7b190dca885e4c861cc0436d3593d5cc9699a8eade753df6
Timestamp: 1718527221 Timestamp [UCT]: 2024-06-16 08:40:21 Age [y:d:h:m:s]: 00:222:15:13:48
Block: 1045362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159259 RingCT/type: yes/0
Extra: 0118c45d6de84c980b7b190dca885e4c861cc0436d3593d5cc9699a8eade753df602110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdf7273579ce1648494c7d10599d62387de7282bd435963639006996f1a37ac2 0.600000000000 1514911 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": 1045372, "vin": [ { "gen": { "height": 1045362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdf7273579ce1648494c7d10599d62387de7282bd435963639006996f1a37ac2" } } ], "extra": [ 1, 24, 196, 93, 109, 232, 76, 152, 11, 123, 25, 13, 202, 136, 94, 76, 134, 28, 192, 67, 109, 53, 147, 213, 204, 150, 153, 168, 234, 222, 117, 61, 246, 2, 17, 0, 0, 0, 8, 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