Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3441b899d5e750d43e7b047ae519b8bf19dd1f5c6f7e537691b390e9013cff

Tx prefix hash: 2f1a9a37a24df278623da9a54e26312c1b7863040f2bf3cc77323419f7e5b723
Tx public key: 2713e973e5c709f0f6763c3b79d60c473fe8957ba3645e9edfdf4d3340519c44
Timestamp: 1684949738 Timestamp [UCT]: 2023-05-24 17:35:38 Age [y:d:h:m:s]: 01:325:12:37:22
Block: 767225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493881 RingCT/type: yes/0
Extra: 012713e973e5c709f0f6763c3b79d60c473fe8957ba3645e9edfdf4d3340519c4402110000000575e3f0e9000000000000000000

1 output(s) for total of 1.761429488000 dcy

stealth address amount amount idx
00: c94c2b96c196472b2a7981fb73402d841be95a20db8792be63d7bf239f71b6c7 1.761429488000 1216336 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": 767235, "vin": [ { "gen": { "height": 767225 } } ], "vout": [ { "amount": 1761429488, "target": { "key": "c94c2b96c196472b2a7981fb73402d841be95a20db8792be63d7bf239f71b6c7" } } ], "extra": [ 1, 39, 19, 233, 115, 229, 199, 9, 240, 246, 118, 60, 59, 121, 214, 12, 71, 63, 232, 149, 123, 163, 100, 94, 158, 223, 223, 77, 51, 64, 81, 156, 68, 2, 17, 0, 0, 0, 5, 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