Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91501ed60eddc68686065f46dc916cdbfa8379b0cca5d9d7f8e01cb9a83a3009

Tx prefix hash: 69ea69a1c53dd1eadd10143eba3d06131a387d5d0838fcfa8e64eb2abb4c0c4d
Tx public key: ea89dab5a3117e122344242f95afab52f2f60aaf5eaf42f1dd37ce5289dac093
Timestamp: 1722430043 Timestamp [UCT]: 2024-07-31 12:47:23 Age [y:d:h:m:s]: 00:303:16:39:35
Block: 1077706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216992 RingCT/type: yes/0
Extra: 01ea89dab5a3117e122344242f95afab52f2f60aaf5eaf42f1dd37ce5289dac093021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f35c0df2d96c38f58139c94c527efb7f76fff2a71ac770de6c59185c9d4a7769 0.600000000000 1550261 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": 1077716, "vin": [ { "gen": { "height": 1077706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f35c0df2d96c38f58139c94c527efb7f76fff2a71ac770de6c59185c9d4a7769" } } ], "extra": [ 1, 234, 137, 218, 181, 163, 17, 126, 18, 35, 68, 36, 47, 149, 175, 171, 82, 242, 246, 10, 175, 94, 175, 66, 241, 221, 55, 206, 82, 137, 218, 192, 147, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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