Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfdede138b40a443f93bbe563aa1b4bd872070bfb584984154d4ec77c12b3930

Tx prefix hash: 75688597719c0fb0fdd847e58a25cc4e50f405ce2f7fab150b458196e29071a2
Tx public key: 855120d91233b54a6b3586a1a825f0cad8d1bc05619182124f40a7c8a4b1d329
Timestamp: 1697665036 Timestamp [UCT]: 2023-10-18 21:37:16 Age [y:d:h:m:s]: 01:181:06:24:31
Block: 872586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390581 RingCT/type: yes/0
Extra: 01855120d91233b54a6b3586a1a825f0cad8d1bc05619182124f40a7c8a4b1d32902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.788424984000 dcy

stealth address amount amount idx
00: 1e57d3cd3df6411e2879e4d128d5d06151a4e00876111c3686dec95359da72e8 0.788424984000 1327676 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": 872596, "vin": [ { "gen": { "height": 872586 } } ], "vout": [ { "amount": 788424984, "target": { "key": "1e57d3cd3df6411e2879e4d128d5d06151a4e00876111c3686dec95359da72e8" } } ], "extra": [ 1, 133, 81, 32, 217, 18, 51, 181, 74, 107, 53, 134, 161, 168, 37, 240, 202, 216, 209, 188, 5, 97, 145, 130, 18, 79, 64, 167, 200, 164, 177, 211, 41, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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