Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9708c3444a1bda3d8d1f1fdc1e0830ba3b5ec3319bf5b144cf06b2f31894725

Tx prefix hash: 8ac07826291e2d90aad110f54cf489e9f38449162f63accc0fbb4f33c87c9ecf
Tx public key: e7717f1290f2d805dedbd12b23907938f85518d7b36d22360c43f699f8937a9e
Timestamp: 1682870803 Timestamp [UCT]: 2023-04-30 16:06:43 Age [y:d:h:m:s]: 01:342:14:51:07
Block: 749988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506113 RingCT/type: yes/0
Extra: 01e7717f1290f2d805dedbd12b23907938f85518d7b36d22360c43f699f8937a9e02110000000275e3f0e9000000000000000000

1 output(s) for total of 2.008993929000 dcy

stealth address amount amount idx
00: 8379cfcfaf863a903059c3e9e7e482c94e3ade9aa8bc4643d880d76128517f2a 2.008993929000 1198017 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": 749998, "vin": [ { "gen": { "height": 749988 } } ], "vout": [ { "amount": 2008993929, "target": { "key": "8379cfcfaf863a903059c3e9e7e482c94e3ade9aa8bc4643d880d76128517f2a" } } ], "extra": [ 1, 231, 113, 127, 18, 144, 242, 216, 5, 222, 219, 209, 43, 35, 144, 121, 56, 248, 85, 24, 215, 179, 109, 34, 54, 12, 67, 246, 153, 248, 147, 122, 158, 2, 17, 0, 0, 0, 2, 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