Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355fa7a27e56fdac21c1d7191114b2744bbb4c1284268b0f80e88c3db969c454

Tx prefix hash: d08a6b0039af65688b42900fbd49a42ec118ff2598ce0e4afe9ba0a5032f5ad1
Tx public key: af2193e731179e2e2ea628b3cb3344042da4020a615de8ca1c30512be582bdb2
Timestamp: 1712907445 Timestamp [UCT]: 2024-04-12 07:37:25 Age [y:d:h:m:s]: 01:210:08:44:37
Block: 998737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409027 RingCT/type: yes/0
Extra: 01af2193e731179e2e2ea628b3cb3344042da4020a615de8ca1c30512be582bdb202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9a00ac8e1ab61f32b66f4e33affff84f4009e9e1c43f32590d6f49cc8e4df89 0.600000000000 1459189 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": 998747, "vin": [ { "gen": { "height": 998737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9a00ac8e1ab61f32b66f4e33affff84f4009e9e1c43f32590d6f49cc8e4df89" } } ], "extra": [ 1, 175, 33, 147, 231, 49, 23, 158, 46, 46, 166, 40, 179, 203, 51, 68, 4, 45, 164, 2, 10, 97, 93, 232, 202, 28, 48, 81, 43, 229, 130, 189, 178, 2, 17, 0, 0, 0, 4, 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